Bump vite and (some) otel packages #882
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
myieye
force-pushed
the
chore/bump-vite-packages
branch
from
ef1c56e to
2dd5cae
Compare
myieye
force-pushed
the
chore/bump-vite-packages
branch
from
2dd5cae to
49dd192
Compare
|
I'm planning to open a follow up PR that removes the lock file, because that's probably the right thing to do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces #874
Initially I deleted the viewer pnpm-lock.yaml, because I realized that it shares the frontend's lockfile. But, I'm not sure how deleting it might affect the local-web-app and mabye other stuff.
So, I temporarily used
shared-workspace-lockfile=false(which seems to be undocumented. pnpm has not convinced me 😉) in.npmrcto update the viewer lock file, which was waaay out of date 😆.